Duplicate Data Types

llandale - Fri Oct 08 16:59:00 EDT 2010
I wonder what would happen if you archived the module and restored it, then practiced simply deleting all the duplicate types that it will let you delete. I'm guessing that while there may be two "ReqTypes" types defined, only one of them is actually in use and DOORS will let you simply delete the other one. Its also possible that the duplicated 'Username' type may not actually be system protected.

If it works in the practice archive, you save and close and open and everything looks good and you can create more attributes with the existing types etc, then it should be good for the production module.

• Louie

Mathias Mamsch - Fri Oct 08 07:16:52 EDT 2010
I think this needs to be fixed on database level. You should ask the IBM support to fix the module for you. This way they will take responsibility if something does not work out.

If you get no response in time, If you want, we can also make a fix. I would need a module archive or the types.dtc file (make a copy, purge all objects and baseline if confidential), I will send you a modifed types.dtc file that you would need to put back to the database repository. We did a similar thing two weeks before, to re-enable the History on the object text attribute. I guess IBM support will do a similar thing.

Did you use the partitioning functionality? Just wondering about the reason for stuff like this.

Regards, Mathias

Mathias Mamsch - Sat Oct 09 14:17:23 EDT 2010

Cite Louie:

... but I cannot help but suspect that his solution will require
you knowing exactly which of the duplicated typesa are indeed
actually in use.

I would have suspected this myself, interestingly neither types nor attributes nor enumeration values have IDs in the DOORS database. It seems the DOORS client will on a rename, not only rename the type but write the new attribute name to all the objects. I am not sure what will happen if the same type is in there two times. Most likely DOORS will ignore the second type.

Regards, Mathias

// types.dtc
[AttrType [WEXP Caption Type] 
 ....
 [Values 
  [ValueName [None] ]  [Number [0] ] 
  [ValueName [Figure] ]  [Number [1] ] 
  [ValueName [Table] ]  [Number [2] ] 
 ]
 ....
]
 
// treedata.dtc
 [Object [201] 
  [ObjectBefore [200] ] 
  [Modified [True]]
  [RichTextAttribute [Created By] [T_StringValue [MMA] ] ]
  ...
  [RichTextAttribute [WEXP Caption] [5] [Figure] ]
  ...
]

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

Doug.Zawacki - Tue Oct 12 12:11:37 EDT 2010
Hi Guys,
Thanks for the interest in this.
Mathias - No partitioning functionality being used here.
with regard to having you perform a fix I am looking into getting this done. We have not yet heard from IBM.

Louie- we have done archives/restores to no avail. We cannot delete system attribute types because they are system types.

Also, as an interesting note, if we add a value to an enumeration the value is reflected in both enumerations. Now we are able to rename "Non-system" enumerations and delete them...but the problem still exists on the "system" attribute types.

I should know later today what our game plan is. I will keep everyone informed. Thanks again for your support, greatly appreciated.

Doug.Zawacki - Tue Oct 12 12:18:42 EDT 2010
One other point. Here is the list of System types that are duplicated.

Real
String
TableCellAlign
TableEdgeType
TableType
Text
User name
YesNo

We cannot delete any of these.
Mathias, I am very interested in knowing the format of the DTC file.